Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1705

reference: 173-tree-1
name: 1705
tree-preservation-order: undefined
173-tpo-1
uprn
address-text
point: POINT (-0.935973 50.862877)
geometry: MULTIPOLYGON (((-0.935888 50.862868,-0.935892 50.862884,-0.935903 50.862900,-0.935922 50.862912,-0.935946 50.862920,-0.935972 50.862922,-0.935998 50.862920,-0.936022 50.862913,-0.936041 50.862901,-0.936054 50.862886,-0.936058 50.862869,-0.936055 50.862853,-0.936043 50.862837,-0.936024 50.862825,-0.936001 50.862817,-0.935974 50.862815,-0.935948 50.862817,-0.935924 50.862824,-0.935905 50.862836,-0.935892 50.862851,-0.935888 50.862868)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL